Information processing apparatus, control method thereof, and storage medium

ABSTRACT

To enable a user to more easily set a rule relating to folder allocation and file naming at the time of filing data, such as a document scanned image and a received facsimile, and storing the file. On a user interface screen for setting a rule relating to property information that is used at the time of allocating a file to a folder for storage, at least a first area for editing the rule and a second area displaying an item a user can select are provided. The item is a unit element for a user to set a character string configuring the property information and corresponds to a character string of an arbitrary attribute a user can set. Then, the rule is created by the item selected by a user from the second area being arranged at a position designated by the user in the first area.

BACKGROUND OF THE INVENTION Field of the Invention

The technique of the present disclosure relates to a technique to set arule at the time of allocating a file to a folder.

Description of the Related Art

Conventionally, in an information processing apparatus, such as an MFP(Multifunctional Peripheral), a method is made use of widely, whichfiles (computerizes) image data obtained by scanning a document orreceived facsimile data and transmits the file to a storage server on anetwork and stores the file therein. Then, at the time of storing thefiled data, automatic allocation of the file to a folder is alsoperformed. For example, Japanese Patent Laid-Open No. 2019-169951 hasdisclosed a technique to automatically perform creation of a folder andallocation of facsimile data to the folder in accordance with a foldernaming rule that is set in advance. It is assumed that as the foldernaming rule in the technique of Japanese Patent Laid-Open No.2019-169951 (in the following, called “prior art”), the attribute name“registered name” is set to the folder name of the first hierarchicallayer, the attribute name “Fax number” is set to the folder name of thesecond hierarchical layer, and the attribute name “reception date” isset to the folder name of the third hierarchical layer, respectively. Inthis case, on a condition that a new facsimile is received, a new folderis created by allocating information (registered name, Fax number,reception date) specified from the received facsimile data to thecorresponding attribute names as each attribute value. The, in thecreated folder, the file of the received facsimile data is stored.

In the case of the above-described prior art, the input fields (firsthierarchical layer to third hierarchical layer) of the attribute nameare determined in advance for each hierarchical layer. For example, itis assumed that a user inputs an attribute value “A” in the input fieldfor the folder in the first hierarchical layer and inputs an attributevalue “B” in the input field for the folder in the second hierarchicallayer. Further, it is assumed that a user desires to create a foldernewly using an attribute value “C” between the first hierarchical layerand the second hierarchical layer. In the case such as this, with theabove-described prior art, it is necessary to change all the inputfields for the folders in the second and subsequent hierarchical layers.Specifically, it is necessary to change the input contents from theattribute value “B” to “C” in the input filed for the new folder in thesecond hierarchical layer and further to input the attribute value “B”in the input field for the new folder in the third hierarchical layer(previous second hierarchical layer). That is, in the case of theabove-described prior art, the hierarchical layers of the folders andthe input fields thereof are fixed, and therefore, in a case where a newfolder is inserted between the folder in the Nth hierarchical layer andthe folder in the (N+1)th hierarchical layer, complicated work isrequired.

Further, in the case of the above-described prior art, the configurationis such that a user is caused to select the attribute name from apulldown menu in each input filed, but it is not possible for a user tocreate a new attribute name and apply it to the folder allocation ruleor the rule relating to file naming.

Consequently, an object of the technique of the present disclosure is tomake is possible for a user to more easily set the rule relating tofolder allocation and file naming at the time of filing data, such as adocument scanned image and a received facsimile, and storing the file.

SUMMARY OF THE INVENTION

The information processing apparatus according to the present disclosureis an information processing apparatus for allocating a file to a folderfor storage, and includes: a display control unit configured to controla display of a user interface screen for setting a rule relating toproperty information that is used at the time of the storage, and theuser interface screen having a first area for editing the rule and asecond area displaying a unit item a user can select, the unit item is aunit element for a user to set a character string configuring theproperty information, the unit item includes a particular itemcorresponding to a character string of an arbitrary attribute a user canset, the rule is created by the unit item selected by a user from thesecond area being arranged at a position designated by the user in thefirst area, and in a case where an attribute name of the particular itemis input by a user, the display control unit arranges the particularitem having the input attribute name at a position designated by a userin the rule which being displayed in the first area and being edited andadds the arranged particular item to the second area.

Further features of the present disclosure will become apparent from thefollowing description of exemplary embodiments with reference to theattached drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram showing an entire configuration of an imageprocessing system;

FIG. 2 is a block diagram showing a hardware configuration of an MFP;

FIG. 3 is a block diagram showing a hardware configuration of an MFPcooperative server and a storage server;

FIG. 4 is a block diagram showing a software configuration of the imageprocessing system;

FIG. 5 is a diagram showing an example of a folder allocation rulesetting screen;

FIG. 6 is a diagram showing an example of the folder allocation rulesetting screen;

FIG. 7 is a diagram showing an example of the folder allocation rulesetting screen;

FIG. 8 is a diagram showing an example of the folder allocation rulesetting screen;

FIG. 9 is a diagram showing an example of the folder allocation rulesetting screen;

FIG. 10 is a diagram showing an example in a case where a set folderallocation rule is displayed;

FIG. 11 is a diagram showing an example of the folder allocation rulesetting screen;

FIG. 12 is a diagram showing an example of the folder allocation rulesetting screen;

FIG. 13 is a diagram shown an example of a file naming rule settingscreen;

FIG. 14 is a diagram showing an example of a property setting screen;

FIG. 15 is a flowchart showing a flow of processing at the time ofsetting a property;

FIG. 16A is a diagram showing an example of the folder allocation rulesetting screen and FIG. 16B is a diagram showing an example of the filenaming rule setting screen;

FIG. 17 is a flowchart showing details of property setting screendisplay processing;

FIG. 18 is a diagram showing the way an attribute value of a customtoken is input on the property setting screen;

FIG. 19 is a diagram showing an example of a scan profile settingscreen;

FIG. 20 is a diagram showing an example of a scan profile editingscreen;

FIG. 21 is a diagram showing an example of a scan profile additionscreen;

FIG. 22 is a diagram showing an example of the scan profile additionscreen;

FIG. 23 is a diagram showing an example of a transmission destinationsetting screen;

FIG. 24 is a diagram showing an example of a custom token normalizationrule setting screen;

FIG. 25 is a flowchart showing details of processing in which anattribute value of a custom token is input on the property settingscreen;

FIG. 26 is a diagram showing the way a custom token normalization ruleis selected on the folder allocation rule setting screen; and

FIG. 27 is a diagram showing the way a custom token normalization ruleis selected on the property setting screen.

DESCRIPTION OF THE EMBODIMENTS

Hereinafter, with reference to the attached drawings, the presentdisclosure is explained in detail in accordance with preferredembodiments. Configurations shown in the following embodiments aremerely exemplary and the present disclosure is not limited to theconfigurations shown schematically.

First Embodiment <System Configuration>

FIG. 1 is a diagram showing the entire configuration of an informationprocessing system according to the present embodiment. The informationprocessing system includes an MFP (Multifunction Peripheral) 110, aclient PC 111, and server apparatuses 120 and 130 that provide cloudservices on the internet. The MFP 110 and the client PC 111 areconnected so as to be capable of communication with various apparatusesproviding various services on the internet via a LAN (Local AreaNetwork).

The MFP 110 is an example of an information processing apparatus havingthe scan function. The MFP 110 is a multifunction peripheral having aplurality of functions, such as the print function and the BOX storefunction, in addition to the scan function. The client PC 111 is aninformation processing apparatus, such as a desktop terminal and amobile terminal, capable of receiving a cloud service via the internet.Both the server apparatuses 120 and 130 are each an informationprocessing apparatus providing cloud services. The server apparatus 120of the present embodiment provides cloud services to perform an imageanalysis for a scanned image received from the MFP 110, transfer arequest from the MFP 110 to the server apparatus 130 providing otherservices, and so on. In the following, the cloud service provided by theserver apparatus 120 is called “MFP cooperative service”. The serverapparatus 130 provides cloud services (hereinafter, called “storageservices”) to store file data sent via the internet in a predeterminedfolder, provide a stored file in response to a request from a webbrowser of the client PC 111, and so on. In the present embodiment, theserver apparatus 120 that provides the MFP cooperative service is called“MFP cooperative server” and the server apparatus 130 that provides thestorage service is called “storage server”.

The information processing system of the present embodiment has theconfiguration including the MFP 110, the client PC 111, the MFPcooperative server 120, and the storage server 130, but theconfiguration is not limited to this. For example, the MFP 110 may playthe role of the client PC 111 and the MFP cooperative server 120.Further, the MFP cooperative server 120 may be arranged on a LAN insteadof the internet. Furthermore, it may also be possible to apply thepresent embodiment to a scene in which a scanned image of a document istransmitted by being attached to a mail by replacing the storage server130 with a mail server or the like.

<Hardware Configuration of MFP 110>

FIG. 2 is a block diagram showing the hardware configuration of the MFP110. The MFP 110 includes a control unit 210, an operation unit 220, aprinter unit 221, a scanner unit 222, and a modem 223. The control unit210 includes each of units 211 to 219 below and controls the operationof the entire MFP 110. The CUP 211 reads control programs (programscorresponding to various functions shown in a software configurationdiagram, to be described later) stored in the ROM 212 and executes theprograms. The RAM 213 is used as a temporary storage area, such as amain memory and a work area, of the CPU 211. In the present embodiment,the one CPU 211 performs each piece of processing shown in flowcharts,to be described later, by using the one memory (RAM 213 or HDD 214), butthe present embodiment is not limited to this. For example, it may alsobe possible to perform each piece of processing by causing a pluralityof CPUs and a plurality of RAMs or HDDs to cooperate with one another.

The HDD 214 is a large-capacity storage unit configured to store imagedata and various programs. The operation unit OF 215 is an interfacethat connects the operation unit 220 and the control unit 210. Theoperation unit 220 is provided with a touch panel, a keyboard and thelike and receives operations/inputs/instructions by a user. The touchoperation to the touch panel includes the operation by a human fingerand the operation by a touch pen. The printer OF 216 is an interfacethat connects the printer unit 221 and the control unit 210. Image datato be printed is transferred from the control unit 210 to the printerunit 221 via the printer OF 216 and printed on a printing medium.

The scanner OF 217 is an interface that connects the scanner unit 222and the control unit 210. The scanner unit 222 generates scanned imagedata by reading a document that is set on a document table or ADF (AutoDocument Feeder), not shown schematically, and inputs the scanned imagedata to the control unit 210 via the scanner OF 217. It is possible toprint (copy and output) the scanned image data generated by the scannerunit 222 in the printer unit 221, store the data in the HDD 214,transmit the data to an external apparatus, such as the MFP cooperativeserver 120, as a file or a mail via a LAN, and so on. The modem OF 218is an interface that connects the modem 223 and the control unit 210.The modem 223 performs facsimile communication of image data with afacsimile device (not shown schematically) on the PSTN. The network OF219 is an interface that connects the control unit 210 (MFP 110) to aLAN. The MFP 110 transmits image data and information to each service onthe internet, receives various kinds of information, and so on by usingthe network OF 219. The hardware configuration of the MFP 110 explainedabove is an example and the hardware configuration may comprise anotherconfiguration as needed or may not have a part of the configuration.

<Hardware Configuration of Client PC and Server Apparatus>

FIG. 3 is a block diagram showing the hardware configuration of theclient PC 111, the MFP cooperative server 120, and the storage server130. The client PC 111, the MFP cooperative server 120, and the storageserver 130 include a CPU 311, a ROM 312, a RAM 313, an HDD 314, and anetwork OF 315. The CPU 311 controls the entire operation by readingcontrol programs stored in the ROM 312 and performing various kinds ofprocessing. The RAM 313 is used as a temporary storage area, such as amain memory and a work area, of the CPU 311. The HDD 314 is alarge-capacity storage unit configured to store image data and variousprograms. The network OF 315 is an interface that connects the client PC111/the MFP cooperative server 120/the storage server 13 to theinternet. The MFP cooperative server 120 and the storage server 130receive requests for various kinds of processing from other apparatuses(MFP 110, the client PC 111 and the like) via the network OF 315 andreturn processing results in accordance with the requests.

<Software Configuration of Information Processing System>

FIG. 4 is a block diagram showing the software configuration of theinformation processing system according to the present embodiment. Inthe following, the software configuration corresponding to the role ofeach of the MFP 110, the MFP cooperative server 120, and the storageserver 130 is explained in order. In the following, explanation is givenby narrowing the various functions possessed by each apparatus to thefunctions relating to the processing up to processing to file a scannedimage obtained by scanning a document in the MFP 110 and store the filein the storage server 130 via the MFP cooperative server 120.

Software Configuration of MFP

The function modules of the MFP 110 are roughly divided into twomodules, that is, a native function module 410 and an additionalfunction module 420. While the native function module 410 is anapplication provided as a standard one in the MFP 110, the additionalfunction module 420 is an application that is installed additionally inthe MFP 110. The additional function module 420 is an application basedon Java (registered trademark) and it is possible to easily implementthe addition of a function to the MFP 110. In the MFP 110, anotheradditional application, not shown schematically, may be installed.

The native function module 410 has a scan execution unit 411 and ascanned image management unit 412. Further, the additional functionmodule 420 has a display control unit 421, a scan control unit 422, acooperative service request unit 423, and an image processing unit 424.

The display control unit 421 displays a user interface screen (UIscreen) for receiving various user operations on a touch panel of theoperation unit 220. The various user operations include, for example,inputting of login authentication information for accessing the MFPcooperative server 120, scan setting, setting of a rule relating tofolder allocation and file naming, instructions to start a scan,instructions to store a file and the like.

The scan control unit 422 gives instructions to perform scan processingto the scan execution unit 411 along with scan setting information inaccordance with the user operation (for example, pressing down of “startscan” button) performed on the UI screen. The scan execution unit 411causes the scanner unit 240 to perform the document reading operationvia the scanner OF 217 and generates scanned image data in accordancewith the instructions to perform scan processing from the scan controlunit 422. The generated scanned image data is stored in the HDD 214 bythe scanned image management unit 412. At this time, the scan controlunit 422 is notified of information on a scanned image identifieruniquely indicating the stored scanned image data. The scanned imageidentifier is a number, symbol, alphabet and the like for uniquelyidentifying the image scanned in the MFP 110. The scan control unit 422acquires, for example, the scanned image data that is the target to befiled from the scanned image management unit 412 by using theabove-described scanned image identifier. Then, the scan control unit422 instructs the cooperative service request unit 423 to make a requestfor processing necessary to file the scanned image data to the MFPcooperative server 120.

The cooperative service request unit 423 makes requests for variouskinds of processing to the MFP cooperative server 120, receivesresponses thereto, and so on. The various kinds of processing include,for example, login authentication, scanned image analysis, transmissionof scanned image data and the like. For transmission and reception withthe MFP cooperative server 120, the communication protocol, such as RESTand SOAP, is used.

The image processing unit 424 generates an image to be used on the UIscreen that is displayed by the display control unit 421 by performingpredetermined image processing for scanned image data.

<<Software Configuration of Server Apparatus>>

First, the software configuration of the MFP cooperative server 120 isexplained. The MFP cooperative server 120 has a request control unit431, an image processing unit 432, a storage server access unit 433, adata management unit 434, and a display control unit 435. The requestcontrol unit 431 stands by in the state of being capable of receiving arequest from an external apparatus and instructs the image processingunit 432, the storage server access unit 433, and the data managementunit 434 to perform predetermined processing in accordance with receivedrequest contents. The image processing unit 432 performs imagemodification processing, such as rotation and inclination correction, inaddition to image analysis processing, such as character area detectionprocessing, character recognition processing, and similar documentdetermination processing, for the scanned image data that is sent fromthe MFP 110. The storage server access unit 433 makes a request forprocessing to the storage server 130. The cloud service has made publica variety of interfaces for storing a file in the storage server,acquiring a stored file, and so on by using the protocol, such as RESTand SOAP. The storage server access unit 433 makes a request to thestorage server 130 by using an interface having been made public. Thedata management unit 434 stores and manages user information, variouskinds of setting data and the like, which are managed in the MFPcooperative server 120. The display control unit 435 receives a requestfrom a web browser running on the MFP 110 or the client PC 111 connectedvia the internet and returns screen configuration information (HTML, CSSand the like) necessary for the screen display. It is possible for auser to check the registered user information, change the scan settingand the setting of the rule relating to folder allocation and filenaming via the screen that is displayed on the web browser.

Next, the software configuration of the storage server 130 is explained.The storage server 130 has a request control unit 441, a filearrangement unit 442, and a display control unit 443. The requestcontrol unit 441 stands by in the state of being capable of receiving arequest from an external apparatus and in the present embodiment,instructs the file arrangement unit 442 to store a received file andread a stored file in response to a request from the MFP cooperativeserver 120. Then, the request control unit 441 returns a response inaccordance with the request to the MFP cooperative server 120. Thedisplay control unit 443 receives a request from a web browser runningon the MFP 110 or the client PC 111 connected via the internet andreturns screen configuration information (HTML, CSS and the like)necessary for the screen display. It is possible for a user to check andacquire a stored file via the screen that is displayed on the webbrowser.

Although omitted in FIG. 4 , it is assumed that the client PC 111 alsocomprises the same function module as the additional function module 420described previously.

<Setting of Folder Allocation Rule>

Following the above, the setting of a rule relating to storagedestination folder allocation in a scene in which a document scannedimage is filed and stored in the storage server 130 is explained. In thepresent embodiment, explanation is given on the assumption that varioussettings including the folder allocation rule setting are performed inthe client PC 111. The control of the display of various UI screens andstorage of the set rule, to be described below, is implemented by theadditional function module 420 described previously comprised by theclient PC 111. That is, it is also possible to perform the contents thatare described below by the MFP 110 comprising the additional functionmodule 420.

FIG. 5 is a diagram showing an example of a UI screen (in the following,called “folder allocation rule setting screen”) for a user to set a rulerelating to a file allocation destination (storage destination folder),which is displayed on the display (not shown schematically) of theclient PC 111. A file folder allocation rule setting screen 500 shown inFIG. 5 shows the initial display state and has four areas, that is, arule editing area 501, a system token area 502, a delimiter token area503, and a custom token area 504. Then, in the rule editing area 501, atoken drop area 507 exists and further, at the bottom part on thescreen, a “Store” button 505 for settling and storing the set ruleexists.

In the present specification, “token” means a unit item for a user todesignate a character string (including symbol) that is used forproperty information necessary at the time of storing a file in thestorage server 130 with the attribute thereof in mind. Then, the tokenincludes a general token (general item) corresponding to a characterstrong of the attribute determined in advance and a particular token(particular item) corresponding to a character string of an arbitraryattribute a user can customize and freely set. A system token and adelimiter token, to be described later, correspond to the general tokenand a custom token, to be described later, corresponds to the particulartoken. These tokens are represented as UI elements that are the targetof the user operation, such as the drag operation and the dropoperation, on various setting screens that appear in the following.

In the system token area 502, the delimiter token area 503, and thecustom token area 504, various tokens are displayed in a list. Then, inthe rule editing area 501, a folder allocation rule that is created byusing various tokens is displayed. Here, the folder allocation ruleincludes information relating to the folder path of the allocationdestination (storage destination folder) of scanned data and thehierarchical structure of the folder, and is set in advance by a user.

<Setting of Token>

It is possible for a user to select one from among the tokens displayedin the system token area 502, the delimiter token area 503, and thecustom token area 504 by the drag operation and perform the dropoperation of the token into the token drop area 507. As a result ofthat, a new folder is represented in a pseudo manner, which includes thecharacter string corresponding to the token selected by the dragoperation in the folder name (folder path).

The system token area 502 is an area in which the token that takes anenvironment variable of a user, such as “Display name of login user”,“Time”, and “Date”, as the attribute value is displayed. The delimitertoken area 503 is an area in which the token that takes the delimiter(symbol), such as “Underscore” and “Hyphen”, as the attribute value isdisplayed. The custom token area 504 is an area in which the token thattakes an arbitrary character string selected (or input manually) fromthe OCR results (recognized character string) of the scanned image asthe attribute value. It is possible for a user to freely create thecustom token. For example, in a case where a user drops a token 506 of“Create token by drag” displayed in the custom token area 504 into thetoken drop area 507, an input field for inputting an attribute nameindicating the token is displayed. That is, the character string of“Create token by drag” displayed on the token 506 has a meaningdifferent from that of the character string displayed on the systemtoken and the delimiter token. In a case of the token 506, the token 506is not the attribute name itself indicating the contents of the tokenbut plays a role of an explanatory sentence prompting a user to input anattribute name and create a new token. Details of the custom token, suchas a specific setting method of an attribute name that is attached tothe custom token, will be described later.

The information on the rule displayed in the rule editing area 501 istransmitted to the MFP cooperative server 120 in response to pressingdown of the “Store” button 505 and managed by the data management unit434. Further, in a case where a “Back” button is pressed down, the rulebeing display in the rule editing area 501 is discarded and the settingprocessing is terminated.

Here, the storage destination folder allocation rule in the presentembodiment is reviewed. First, it is assumed that restrictions are notimposed particularly on the combination and order of the tokens that canbe set as the folder allocation rule. For example, it may also bepossible to create a rule to configure one folder name only by thedelimiter tokens in the delimiter token area 503 or it is also possibleto create a rule using only the same system token. However, it isassumed that the contents of each token displayed in the system tokenarea 502 and the delimiter token area 503 cannot be changed. On theother hand, as regards the custom token, it is assumed that theattribute name of the custom token displayed in the custom token area504 can be changed freely and the custom token itself can be deleted.

FIG. 6 shows the state of the folder allocation rule setting screen 500in a case where a user drags and drops an arbitrary system token withinthe system token area 502 into the rule editing area 501. Specifically,FIG. 6 shows the state in a case where a system token 511 that takes“Display name of login user” as the attribute name among the pluralityof system tokens displayed within the system token area 502 is droppedinto the token drop area 507. In the rule editing area 501 in FIG. 6 ,at the position of the token drop area 507 (see FIG. 5 ) at which a userhas performed the drop operation, a token 508 that takes “Display nameof login user” as the attribute name is arranged newly and at the sametime as that, new token drop areas 514 and 515 are generated. In thestate shown in FIG. 6 , in a case where a user selects one token fromthe token groups existing in the various token areas 502 to 504described above and drags and drops the token into the token drop area514, a new token drop area is further generated (not shownschematically). Then, in a case where a user further drags and drops anarbitrary token into the newly generated token drop area, a furthertoken drop area is generated. The state of the folder allocation rulesetting screen 500 after the operation such as this is performedrepeatedly is shown in FIG. 7 . In the rule editing area 501 in FIG. 7 ,two tokens (token 516 that takes “{Space}” as attribute name and token517 that takes “Name of scan profile” as attribute name) are newly addedand further, a token drop area 518 is generated. In this case, the threetokens 508, 516, and 517 are set to the folder name of the folder in thefirst hierarchical layer (highest hierarchical layer). According to theexample in FIG. 7 , the folder that takes “(Display name of login user)(Name of scan profile)” as the folder path is created as the folder inthe highest hierarchical layer. On the other hand, in the rule editingarea 501 shown in FIG. 6 , also in a case where a user drags and dropsone arbitrary token into the token drop area 515 exiting in the secondhierarchical layer, a new token drop area is generated further. In therule editing area 501 in FIG. 7 , a token 519 of “Date (year, fourdigits)” is added and two token drop areas 502 and 521 are furthergenerated. The token drop area 521 is used at the time of adding a newtoken to the folder in the second hierarchical layer, which hasdetermined to use the token 519. Further, the token drop area 520 isused at the time of setting the first token to the folder in the thirdhierarchical layer.

As is obvious from the explanation given so far, the hierarchical layerof the folder that uses the three tokens 508, 516, and 517 as the foldername and that of the folder that uses the token 519 as the folder nameare different (see FIG. 7 ). That is, in the folder structure, thefolder that uses the token 519 as the folder name exists in the layerlower than that of the folder that uses the three tokens 508, 516, and517 as the folder name. Even for the tokens that are set in the ruleediting area 501 as described above, it is possible to change thearrangement by the drag operation, such as exchanging adjacent tokensand inserting a token between tokens.

<<Deletion of Token>>

Following the above, a case is explained where a user deletes a token ineach folder hierarchical layer that is set as described above. In a casewhere a user performs the mouse hover operation for one of the tokensbeing displayed in the rule editing area 501, a “x” button (not shownschematically) is displayed on the token. It is possible for a user todelete any token by pressing down the “x” button. FIG. 8 shows the stateof the folder allocation rule setting screen 500 after the token that isset in the rule editing area 501 is deleted by the above-describeddeletion operation. In the rule editing area 501 in FIG. 8 , UI blocks522 and 523 of “Deleted” are displayed at the positions at which tokensare deleted. These UI blocks 522 and 523 displayed as “Deleted” functionas a token drop area and in a case where a user drags and drops a newtoken into the UI block, at the position displayed as “Deleted”, a newtoken is set. As described above, in the present embodiment, even in acase where the token being displayed in the rule editing area 501 isdeleted, the area in which the token has been present is maintained.However, it may also be possible to produce a display in which the areafrom which the token has been deleted is clipped in place of displayingthe “Deleted” UI block and making it possible to arrange a new tokentherein. In a case where a user presses down the “Store” button 505 inthe state in FIG. 8 , the folder allocation rule setting screen 500transitions to a state shown in FIG. 9 and the “Deleted” UI block is nolonger displayed.

<<Check of Set Folder Allocation Rule>>

FIG. 10 is a diagram showing an example of the state where a folderallocation rule created and stored by a user via the folder allocationrule setting screen 500 described previously is displayed on a mainscreen, not shown schematically. In the example shown in FIG. 10 , afolder path 1001 in which the demarcation between folder hierarchicallayers is indicated by a slash is displayed. The folder path 1001 shownin FIG. 10 corresponds to the results of setting a predetermined tokento each of the folders in the first hierarchical layer to the thirdhierarchical layer as in the rule editing area 501 in FIG. 12 , to bedescribed later. In a case of following the tokens that are set in therule editing area 501 shown in FIG. 8 , the contents of the folder paththat is displayed are “{Display name of login user}/Date (month)”. Thatis, in a case of FIG. 8 , the token for the folder in the secondhierarchical layer is deleted and the folder path in accordance with thetokens that are set respectively to the folders in the firsthierarchical layer and the third hierarchical layer is displayed. Asdescribed above, in a case where the token for the folder in a specifichierarchical layer no longer exists because the set token is deleted,the folder path in the state where the folder in the hierarchical layeris clipped is displayed.

<Custom Token>

Following the above, the user operation in a case where a folderallocation rule is set by using the custom token, which is the featureof the present embodiment, and transition of the UI screen accompanyingthe user operation are explained. FIG. 11 shows the state of the folderallocation rule setting screen in a case where a user drops the customtoken 506 into the token drop area in the third hierarchical layer inthe rule editing area 501. Here, in the token drop area for which thedrop operation of the custom token 506 has been performed, a characterstring 1100 of “Adding . . . ” is displayed and further, in a text field1101 that is displayed in a pop-up manner in accordance with the dropoperation, a character string of “Company name” is input. The characterstring that is input in the text field 1101 in this manner is set as theattribute name of the token for the folder in the third hierarchicallayer by a “Store” button 1102 within the text field 1101 being presseddown. A “Cancel” button is used in a case where the setting of thecustom token is cancelled.

FIG. 12 shows the state of the folder allocation rule setting screen 500after the custom token is set by the “Store” button 1102 being presseddown by a user. A token 1201 having the character string “Company name”that is input in the text field 1101 described above as the attributename is displayed as the token for the folder in the third hierarchicallayer within the rule editing area 501. Further, in the custom tokenarea 504, a custom token 1201 having the character string “Company name”as the attribute name is displayed so that it is possible to make use ofagain the custom token created this time. The timing at which thecharacter string that is input in the text field 1101 is stored as theattribute name of the custom token that can be made use of again may beimmediately after the attribute name is input in the text field 1101(that is, before the “Store” button 1102 is pressed down). Further, itis assumed that also in a case where a token whose contents are the sameas those of the attribute name already existing as the system token orthe delimiter token is created as a new custom token, the token is addedto the custom token area 504 as a new custom token. However, it isassumed that even in a case where the same character string as that ofthe attribute name of the custom token already existing in the customtoken area 504 is input in the text field 1101, the custom token havingthe same attribute name is not displayed in the custom token area 504 ina duplicate manner. In a case where the character string that is alreadyused as the attribute name of the already existing custom token is inputin the text field 1101, it may also be possible to notify a user of thisby displaying a message to the effect that the character string cannotbe used as the attribute name, and so on. Alternatively, it may also bepossible not to perform addition to the custom token area 504 whilepermitting the input of the above-described already used characterstring in the text field 1101 or the setting itself of the custom tokenbased on the input. Further, it may also be possible to prevent, even ina case where a custom token having the same attribute name as that ofthe system token or the delimiter token is created, registration orutilization thereof as a custom token.

<Setting of Extraction Rule and Verification Rule of Custom Token>

A setting method of setting a character string extraction rule and acharacter string verification rule for a custom token is explained. Inthe present embodiment, explanation is given by taking a case as anexample where the setting of the character string extraction rule andthe character string verification rule is also performed in the clientPC 111.

The character string extraction rule is a rule to normalize (extractionor deletion) a value that is input in the attribute value input field atthe time of property setting. That is, the character string extractionrule is a rule that is referred to in a case where a specific characterstring is extracted or deleted from the value that is input in theattribute value input field. On the other hand, the character stringverification rule is a rule to verify a value that is input in theattribute value input field at the time of property setting. In a casewhere the character string that is input in the attribute value inputfield is not in accordance with the specified format as a result ofverifying the character string verification rule, a user is warned aboutthat.

FIG. 24 is a diagram showing an example of a UI screen (in thefollowing, called “custom token normalization rule setting screen”) fora user to set the character string extraction rule and the characterstring verification rule that are displayed on the display of the clientPC 111. A custom token normalization rule setting screen 2400 shown inFIG. 24 shows the initial display state. The display method of thecustom token normalization rule setting screen 2400 is not limited inparticular. For example, on the folder allocation rule setting screen500 in FIG. 11 and FIG. 12 , the custom token normalization rule settingscreen 2400 is displayed at the timing a registered custom token isselected. Alternatively, it may also be possible to set a custom tokenregistration screen (not shown schematically) separately and display thecustom token normalization rule setting screen 2400 at the timing an“Add” button within the custom token registration screen is pressed downand an attribute name is input subsequently.

On the custom token normalization rule setting screen 2400, each settingitem of Display name 2401, Default value 2402, Data extraction rule2403, and Data verification rule 2404 exists. By inputting an arbitrarycharacter string within the text field corresponding to each settingitem, the setting value of each setting items is determined. In Displayname 2401, an attribute name is set. In Default value 2402, it ispossible to set a value that is input by default in the attribute valueinput field. In Data extraction rule 2403, it is possible to set theabove-described character string extraction rule. In Data verificationrule 2404, it is possible to set the above-described character stringverification rule. Default value 2402, Data extraction rule 2403, andData verification rule 2404 may be left empty or it may also be possibleinput values in an arbitrary combination thereof.

Further, the format in which a setting value is input in Data extractionrule 2403 and Data verification rule 2404 is not limited. For example, aformat is considered in which alternatives are displayed in a pulldownformat and a setting value is selected therefrom, in addition to aformat in which a user directly inputs a regular expression. Forexample, in a case where it is desired to set a rule to delete thecharacter string “Inc.” included in the trade name as the characterstring extraction rule, it may also be possible to implement this bydirectly inputting “.+(?=Inc.)|(?<=Inc.).+” in Data extraction rule2403. Further, in a case where it is desired to set a rule to verifywhether an input character string includes only single-byte figures asthe character string verification rule, it may also be possible toimplement this by directly inputting “[0-9]+” in Data verification rule2404. In place of the direct input such as this, as an example in whichalternatives are displayed, for example, for the character stringextraction rule, an alternative, such as “Delete trade name such asInc.” is displayed. Alternatively, it is considered to displayalternatives, such as “Date format: YYYYMMDD” and “Date format: MM DD,YYYY”, are displayed for the character string verification rule.

<Setting of File Naming Rule>

Following the above, the setting of a naming rule relating to a filename that is attached in a case where a scanned image or the like isfiled is explained. In the present embodiment, explanation is given bytaking a case as an example where the setting of the file naming rule isalso performed in the client PC 111. FIG. 13 is a diagram showing anexample of a UI screen (in the following called “file naming rulesetting screen”) for a user to set a file naming rule, which isdisplayed on the display (not shown schematically) of the client PC 111.A File Naming Rule setting screen 1300 shown in FIG. 13 shows theinitial display state and the screen configuration is similar to that ofthe folder allocation rule setting screen 500 described previously. Thatis, the File Naming Rule setting screen 1300 also has four areas, thatis, a rule editing area 1301, a system token area 1302, a delimitertoken area 1303, and a custom token area 1304. Then, in the rule editingarea 1301, a token drop area 1305 exists and further, at the bottom parton the screen, a “Store” button 1306 for setting and storing the setfile naming rule exists. In the following, points different from thoseof the folder allocation rule setting screen 500 are explained mainly.

The creation of a file naming rule is also performed by arrangingvarious tokens displayed in the system token area 1302, the delimitertoken area 1303, and the custom token area 1304 in the rule editing area1301 by drag and drop. The difference from the folder allocation rulesetting screen 500 lies in that in a case of a file name, the structureis not a hierarchical structure and even in a case where a new token isadded to the rule editing area 1301, a plurality of token drop areas isnot displayed.

One or a plurality of tokens arranged in the rule editing area 1301 is acomponent or components of a single file name. That is, in a case wherea plurality of tokens is set, one file name is generated by connectingthe attribute value of each token.

Here, in the custom token area 1304 on the File Naming Rule settingscreen 1300, a custom token 1311 that takes “Company name” as theattribute name and a custom token 1312 that takes “Estimate form” as theattribute name are displayed. Of these two custom tokens, the customtoken 1311 of “Company name” corresponds to the custom token 1202 thatis created on the folder allocation rule setting screen 500 describedpreviously. That is, the custom token 1311 is the custom token that iscreated at the time of setting of the folder allocation rule isdisplayed as a custom token that can be made use of also at the time ofsetting of the file naming rule. Similarly, the custom token 1312 of“Estimate form” that is displayed in the custom token area 1304 on theFile Naming Rule setting screen 1300 is also displayed in the customtoken area 504 after the creation thereof in a case where the folderallocation rule setting screen 500 is opened. In this manner, it ispossible to share custom tokens between the folder allocation rulesetting screen and the file naming rule setting screen.

<Property Setting at the Time of Filing>

Next, a flow of specific processing in the property setting at the timeof filing a scanned image or the like is explained. Here, the propertyrefers to a file name, a folder path, metadata and the like, which arenecessary for each piece of filing-target data. For example, in a casewhere a certain document is scanned and filed, and stored in the storageserver 130, a user sets a necessary property via a property settingscreen on which the storage destination folder allocation rule and thefile naming rule are reflected, which are set as described above.

FIG. 14 is a diagram showing an example of the property setting screen.A property setting screen 1400 shown in FIG. 14 is in the initialdisplay state and has a two-pane configuration of a preview pane 1401and a property pane 1402. Here, within the preview pane 1401, thescanned image of a business form of “Estimate form” ispreview-displayed. In the preview pane 1401, it is possible to displayan arbitrary position in the scanned image by scrolling and zooming thescanned image. The property pane 1402 is a pane for displaying andediting a property to be attached to the processing-target scannedimage. Here, within the property pane 1402, a folder path display area1403, a file name display area 1404, an attribute value input field 1405corresponding to a folder path, and an attribute value input field 1406corresponding to a file name are displayed. Then, “/tokita/{Companyname}/2020.02.27” displayed in the folder path display area 1403 isbased on the folder allocation rule that is set on the folder allocationrule setting screen 500 described previously. Further, “{Estimateform}_20200227_{Company name}_1” displayed in the file name display area1404 is based on the file name naming rule that is set on the FileNaming Rule setting screen 1300. Details of the display of a folder pathand a file name based on each rule will be described later.

<Flow of Property Setting Processing>

FIG. 15 is a flowchart showing a flow of processing at the time of auser setting a property of a file via the above-described propertysetting screen 1400 on the MFP 110. The execution of this flow starts bythe display control unit 421 of the MFP 110 receiving user instructionsto open the property setting screen 1400 as a trigger. Here, it isassumed that as the folder allocation rule and the file naming rule, thefollowing contents shown on the setting screens in FIG. 16A and FIG. 16Bare set respectively.

<<Setting Contents of Folder Allocation Rule>>

“‘Display name of login user’ (system token)/‘Company name’ (customtoken)/‘Year’ (system token) ‘period’ (delimiter token) ‘Month’ (systemtoken) ‘period’ (delimiter token) ‘Day’ (system token)” <<Settingcontents of file naming rule>>

-   -   “‘Estimate form (custom token)’ ‘Underscore (delimiter token)’        ‘Year (system token)’ ‘Month (system token)’ ‘Day (system        token)’ ‘Underscore (delimiter token)’ ‘Company name (custom        token)’”

<<Setting Contents of Custom Token Normalization Rule of Company Name(Custom Token)>>

-   -   “Display name: Company name, Default value: Empty, Data        extraction rule: “.+(?=Inc.|(?<=Inc.).+” (Delete Inc. at top or        end), Data verification rule: “.+” (not Empty)

In the following, a detailed explanation is given along the flow in FIG.15 . In the following explanation, symbol “S” represents a step.

First, at S1501, information on the folder allocation rule that is setby a user is acquired. At S1502 that follows, information on the filenaming rule that is set by a user is acquired. At next S1503 and S1504,processing to acquire the attribute value of the system token includedin the information acquired at S1501 and S1502 is repeated the number oftimes corresponding to the number of system tokens. Specifically, thecharacter string corresponding to the environment variable of a user,which corresponds to the system token, is acquired from the datamanagement unit 434 of the MFP cooperative server 120. For example, forthe system tokens “Year”, “Month”, and “Day”, character strings “2020”,“2”, and “27” representing the date of the scan are acquired,respectively. Further, for the system token “Display name of loginuser”, the character string “tokita” representing the user name of theuser registered in the system is acquired. In the case of theabove-described example, the four system tokens are included in thefolder allocation rule and the three system tokens are included in thefile naming rule, and therefore, the attribute value acquisition isrepeated seven times. In a case where no system token is included ineach rule, the processing at S1503 and S1504 is skipped and theprocessing advances to step S1505. The attribute value of the systemtoken changes dynamically in accordance with the system setting, unlikethose of the custom token and the delimiter token. Because of this, itis necessary to update the corresponding character string (attributevalue) of each system token each time the system setting is changed.

At S1505, by using the folder allocation rule acquired at S1501 and thecharacter string of each system token, which is acquired at S1504, afolder path is generated. At S1506 that follows, by using the filenaming rule acquired at S1502 and the character string of each systemtoken, which is acquired at S1504, a file name is generated. At thistime, as regards the delimiter token, the relevant delimiter, such as aperiod and a space, is input. Further, as regards the custom token, thecharacter string of the corresponding attribute name is inputtemporarily.

At next S1507, the property setting screen 1400 described previously isdisplayed on the display (not shown schematically) of the client PC 111.FIG. 17 is a flowchart showing details of property setting screendisplay processing. In the following, a detailed explanation is givenalong the flow in FIG. 17 .

At S1701, the folder path generated at S1505 is displayed in the folderpath display area 1403 on the property setting screen 1400. As describedpreviously, in the example in FIG. 14 , “/tokita/(Companyname)/2020.02.27” is displayed. In this case, for the system token thattakes “Display name of login user” as its attribute name, the characterstring “tokita” is input. Further, for the custom token that takes“Company name” as its attribute name, a character string is to be inputby, for example, selecting a desired text block from the scanned image,and therefore, in the current stage, the character string of “Companyname” indicating the attribute name is input temporarily. Then, for eachsystem token that takes each of “Year”, “Month”, and “Day” as itsattribute name, figures “2020”, “02”, and “27” representing the date ofacquisition of the scanned image within the preview pane 1401 are inputwith “. (Period)” that is the delimiter token being sandwiched inbetween. In a case where the date of execution of the scan changes, thefigures allocated to these system tokens change each time.

At S1702, whether or not a custom token is included in the folderallocation rule acquired at S1501 is determined. In a case where acustom token is included, the processing advances to S1703 and in a casewhere no custom token is included, the processing advances to S1705. Inthe example described above, the custom token that takes “Company name”as the attribute name is included, and therefore, the processingadvances to S1703.

At S1703 and S1704, processing to display the attribute value inputfiled 1405 for the custom token is repeated the number of timescorresponding to the number of custom tokens included in the folderallocation rule. In the example described above, one custom token isincluded in the folder allocation rule, and therefore, one attributevalue input field is displayed (see FIG. 14 ), but in a case where aplurality of custom tokens is included, a plurality of attribute valueinput fields is displayed. In a case where no custom token is includedin the folder allocation rule (No at S1702), the attribute value inputfield is not displayed.

At next S1705, the file name generated at S1506 is displayed in the filename display area 1404 on the property setting screen 1400. As describedpreviously, in the example in FIG. 14 , “{Estimateform}_20200227_{Company name}_1” is displayed. In this case, for thesystem tokens of “Year”, “Month”, and “Day”, figures of “2020”, “02”,and “27” representing the date of acquisition of the scanned imagewithin the preview pane 1401 are displayed in the state of beingconnected without using delimiters. Further, for the custom tokes thattake “Estimate form” and “Company name” as the attribute namesrespectively, as described above, the character strings indicating theattribute names respectively are input temporarily.

At S1706, whether or not a custom token is included in the file namingrule acquired at S1502 is determined. In a case where a custom token isincluded, the processing advances to S1707 and in a case where no customtoken is included, this processing is exited. Here, as described above,the custom tokens that take “Estimate form” and “Company name” as theattribute names respectively are included, and therefore, the processingadvances to S1707.

At S1707 and S1708, processing to display the attribute value inputfield 1406 for the custom token is repeated the number of timescorresponding to the number of custom tokens included in the file namingrule. In the example described above, two custom tokens are included inthe file naming rule, and therefore, two attribute value input fields1406 are displayed (see FIG. 14 ). In a case where no custom token isincluded in the file naming rule (No at S1706), the attribute valueinput field 1406 is not displayed.

The above is the contents of the property setting screen displayprocessing. As described above, in the present embodiment, at the timeof creating a rule for a folder path or a file name, it is possible touse a common token (custom token, system token). Then, even though acommon token is used, the folder path and the file name are displayed ina distinct manner in the property pane 1402.

FIG. 18 shows the way the attribute value of a custom token is input bya user on the property setting screen 1400 after the property settingscreen display processing described above is completed. In the attributevalue input fields 1405/1406 corresponding to each custom token, anattribute name 1801, an attribute value 1802, and a cutout image 1803corresponding to the attribute value are displayed. In a case where auser has not selected yet a text block including the attribute value(character string) of the custom token from the preview pane 1401, theattribute value 1802 is displayed as “None (empty)” as in the attributevalue input field 1406 of the custom token that takes “Estimate form” asthe attribute name. Further, the cutout image 1803 corresponding to theattribute value is also blank.

A user who inputs the attribute value of a custom token first selectsthe attribute value input field of the target custom token from amongthe attribute value input fields displayed in the property pane 1402.Here, in FIG. 18 , the attribute value input field 1405 is selected andhighlighted. In this state, a user designates (for example, performs theclick operation for) a text block including the attribute value(character string) of a custom token from the scanned image displayed inthe preview pane 1401. The text block for which the click operation hasbeen performed is highlighted by being attached with a fame line or acolor within the preview pane 1401. At the same time as this, in theattribute value input field 1405 being selected within the property pane1402, the character string included in the designated text block isdisplayed as the attribute value 1802. At this time, in the attributevalue 1802, the value after the data extraction rule and the dataverification rule set on the “custom token normalization rule settingscreen” described previously are applied is displayed. Further, theimage portion corresponding to the text block is displayed as the cutoutimage 1803 corresponding to the attribute value. In a case where theattribute value is input to the custom token, the contents thereof arereflected in the folder path display area 1403 and the file name displayarea 1404.

Here, with reference to a flowchart shown in FIG. 25 , processing isexplained in which the value of a text block selected by a user is inputin the attribute value input field. In the following explanation, symbol“S” represents a step.

First, at S2501, the selection operation of a text block by a user isdetected. At S2502 that follows, whether the attribute value input fieldis selected is determined. In a case where the attribute value inputfield is not selected, the processing returns to S2501. In a case wherethe attribute value input field is selected, the processing transitionsto S2503.

At S2503, an OCR character string of the text block selected by the useris acquired. Specifically, a request to analyze the text block relatedto the selection is transmitted from the cooperative service requestunit 423 to the MFP cooperative server 120 and the image processing unit432 performs OCR processing based on the request. Then, the results ofexecution of the OCR processing are returned to the cooperative servicerequest unit 423 and the display control unit 421 acquires the executionresults. For example, in the property pane 1402, in the state where theattribute value input field 1405 of the custom token that takes “Companyname” as the attribute value is selected, the user clicks a text block1804 of “Plastic Mold Inc.” in the preview pane 1401. Then, the OCRprocessing is performed for the text block 1804 as described above and“Plastic Mold Inc.” is acquired as the OCR character string.

Following the above, at S2504, whether the character string extractionrule is set to the selected attribute value input field is determined.In a case where the rule is not set, the processing transitions to S2507and in a case where the rule is set, the processing transitions toS2505.

At S2505, the character string extraction rule that is set is acquired.Here, it is assumed that the character string extraction rule whosecontents are “Delete “Inc.” included in the trade name” is acquired. AtS2506 that follows, data that is the attribute value is extracted inaccordance with the character string extraction rule from the OCRcharacter string acquired at S2503. Here, the OCR character string of“Plastic Mold Inc.” is acquired, and therefore, “Plastic Mold” isextracted, which is obtained by excluding “Inc.” from “Plastic MoldInc.”.

At next S2507, the attribute value is input in the attribute value inputfield. Here, the character string of “Plastic Mold” is input in theattribute value input field 1405 as the attribute value. In a case wherethe attribute value is input as described above, the portion of“{Company name}” in the folder path display area 1403 is replaced with“Plastic Mold”. Further, in the file naming rule also, the custom tokenthat takes “Company name” as the attribute name is set, and therefore,synchronization processing is performed for the attribute value inputfield 1406 thereof. That is, the portion of “{Company name}” in the filename display area 1404 is also replaced with “Plastic Mold” similarly.In a case where a method other than the method of designating anarbitrary text block from the preview pane 1401 is used, for example, ina case where the character string that is the attribute value is inputmanually by using a soft keyboard (not shown schematically) or the like,the synchronization processing is also performed. That is, irrespectiveof the input method of the attribute value, the same attribute value isset to the common custom tokens. In a case where the attribute valueinput field for the custom token for which the attribute value hasalready been set is selected and a text block different from the textblock currently being designated is designated, the existing attributevalue is overwritten by the attribute value newly input.

Following the above, at S2508, whether the character string verificationrule is set to the selected attribute value input field is determined.In a case where the rule is not set, the processing is terminated. In acase where the rule is set, the processing transitions to S2509. AtS2509, the character string verification rule that is set is acquired.Then, at S2510, the attribute value that is input at S2507 is verifiedin accordance with the character string verification rule acquired atS2509. In a case whether the attribute value is not correct as a resultof the verification, the processing transitions to S2511 and a messageto the effect that the input attribute value is not correct is displayed(not shown schematically). On the other hand, in a case where there isno problem in the results of the verification, this processing isterminated.

The user having completed the above-described processing for all thecustom tokens presses down a “Transmit” button 1805. Due to this, thedata of the scanned image is sent from the MFP 110 to the MFPcooperative server 120 along with the information on the folder path andthe file name, which are set on the property setting screen 1400. Then,in the MFP cooperative server 120, the storage server access unit 433files the data of the scanned image by attaching the designated filename thereto by making use of the received information and data andstores the file in the designated folder of the cloud server 130. In acase where the user presses down the “Transit” button 1805 in the emptystate where the attribute value is not set to the custom token, thefolder path and the file name are generated and stored with the portionof the attribute value being left empty. For example, the propertysetting screen 1400 in FIG. 18 is in the state where no attribute valueis set to the custom token that takes “Estimate form” as the attributename. In a case where the “Transit” button 1805 is pressed down in thisstate, the MFP cooperative server 120 requests the storage server 130 tostore the data of the scanned image being displayed in the preview pane1401 under the following conditions.

-   -   storage destination folder: “/tokita/Plastic Mold        Inc./2020.02.27”    -   file name: “_20200227_Plastic_Mold Inc._1”

<Scan Profile>

It is possible to set the folder allocation rule and the file namingrule, which are set as described above, for each of various scanworkflows. Here, the scan workflow means a workflow for transmittingdata of a scanned image obtained by scanning a document, such as abusiness form, to a specific transmission destination (for example, thestorage server 130) under specific conditions. Information on theconditions on each scan workflow and the transmission destination ismanaged by a scan profile. It is possible for a user to easily implementa desired scan workflow by creating in advance a scan profile.

FIG. 19 shows an example of a UI screen (in the following, called “scanprofile setting screen”) for setting a scan profile, which is displayedon the operation unit 220 of the MFP 110 (or client PC 111). A scanprofile setting screen 1900 shown in FIG. 19 includes a side menu area1901 and a menu area 1902. Then, in a case where a user selects “Scan”from items displayed in the side menu area 1901, the screen transitionsto a UI screen (in the following, called “scan profile editing screen”)for performing editing work, such as addition and deletion of a scanprofile, to be described later. In the menu area 1902, a plurality oficons corresponding to scan profiles is displayed. Each time a usercreates a scan profile, an icon corresponding to the scan profile isadded to the menu area 1902. Further, in a case where a button 1903located at the bottom part in the menu area 1902 is pressed down, anicon of another scan profile that has not been displayed is displayedand it is made possible to browse the icon.

The scan profile setting screen 1900 shown in FIG. 19 is a UI screenthat is displayed in a case where a user having a user ID of “user a”logs in to the MFP 110. It may also be possible to make scan profiles tobe displayed different for different users who log in, or a scan profileavailable in a sharing manner to a plurality of users may exist.

It is assumed that a user selects an icon corresponding to an arbitraryscan profile on the scan profile setting screen 1900 and then givesinstructions to perform a scan. Then, the property setting screen 1400is displayed on which to determine a folder name and a file name inaccordance with the folder allocation rule and the file naming rulecorresponding to the selected scan profile. For example, it is assumedthat the following folder allocation rule and the file naming rule areassociated with the scan profile indicated by an icon 1904.

-   -   folder allocation rule: “/{Display name of login user}/{Company        name}/{Year} {Month} {Day}/”    -   file naming rule: “{Estimate form}_{Year}{Month}{Day}_{Company        name}”

In this case, the scanned image that is generated after the icon 1904 isselected is displayed in the preview pane 1401 on the property settingscreen 1400. Then, the folder allocation rule of the above-describedcontents associated with the scan profile corresponding to the selectedicon 1904 is displayed in the folder path display area 1403. Further,the file naming rule of the above-described contents associated with thesame scan profile is displayed in the file name display area 1404.

<<Creation of Scan Profile>>

Next, a method of creating a scan profile is explained. It is made for auser to display a UI screen (in the following, described as “editingscreen”) for editing a scan profile as shown in FIG. 20 by logging in tothe MFP cooperative server 120 via, for example, the client PC 111 andby the screen transition from a main screen (not shown schematically)that is displayed after the login. An editing screen 2000 shown in FIG.20 includes a menu list are 2001, a profile list area 2002, and aprofile setting area 2003. In the profile list area 2002, a scan profilecurrently being created or a list of created scan profiles is displayed.In the profile setting area 2003, the setting contents of the scanprofile selected by a user form the list displayed in the profile listarea 2002 are displayed. The profile list area 2002 and the profilesetting area 2003 are displayed by selecting the item “Scan profile”within the menu list area 2001.

Further, in a case where a button 2004 located at the top part on theediting screen 2000 is pressed down, a UI screen (in the following,described as “addition screen”) for adding a scan profile as shown inFIG. 21 is displayed on the editing screen 2000 in an overlapping mannerand it is made possible to add a new scan profile. On an addition screen2100 shown in FIG. 21 , a plurality of setting tabs 2012 exists and in acase where one tab is selected therefrom, a plurality of setting itemsincluded in the tab is displayed. The example in FIG. 21 shows the statewhere the setting items in a case where the tab of “Output Setting” isselected. In “File name prefix” 2101 among the displayed setting items,a “Setting of file naming rule” button 2103 is displayed. By pressingdown the “Setting of file naming rule” button 2103, the File Naming Rulesetting screen 1300 described previously is displayed and it is madepossible to create and edit the file naming rule.

FIG. 22 shows the state where the setting items in a case where the tabof “Setting of Workflow” within the addition screen 2100 in FIG. 21 isselected are displayed. The displayed setting items include a “Settingof rule of storage destination folder” button 2201 and by selecting thebutton 2201, the folder allocation rule setting screen 500 describedpreviously is displayed. At this time, in a case where the folderallocation rule is already created, on the periphery of (in the examplein FIG. 10 described previously, directly above) the “Setting of rule ofstorage destination folder” button 2201, the already-created folderallocation rule is displayed.

Further, in a case where an “Add” button 2104 existing in the additionscreen 2100 is pressed down after setting various kinds of informationon the scan profile, the addition screen 2100 closes and this time, thescreen switches to a UI screen (in the following, called “transmissiondestination setting screen”) for setting the transmission destination ofthe data of the scanned image that has been filed. FIG. 23 shows anexample of the transmission destination setting screen. On atransmission destination setting screen 2300 shown in FIG. 23 , aplurality of transmission destinations is displayed in a list and in acase where one of them is selected, information on the transmissiondestination relating to the selection is stored in association with thescan profile currently being created.

In a case where the information of the requisite minimum forimplementing a scan workflow is set as described above, the screenreturns to the editing screen 2000 in FIG. 20 . At that time, in theprofile list area 2002, a newly created scan profile is added anddisplayed.

Modification Example

Next, an aspect is explained as a modification example in which it ismade possible for a user to more easily set the character stringverification rule and the character string extraction rule for thecustom token to which a specific attribute name whose use frequency ishigh, such as “Company name” and “Date”, is attached. Here, the specificcustom token according to this modification example is called “attributetype custom token”.

FIG. 26 shows the state of the folder allocation rule setting screen 500in a case where an attribute type custom token 2601 that takes “Companyname” as the attribute name thereof is dropped into the token drop area.Here, under the dropped custom token, a context menu 2602 is displayedin a pulldown format. In this context menu 2602, radio buttons 2602 a to2602 c exist. Each radio button corresponds to “Set normalization ruleof data”, “Delete trade name (Delete characters such as “Inc.” includedin trade name), and “Not set normalization rule of data”. For example, auser who desires to set the data normalization rule selects the radiobutton 2602 a. Then, the character string verification rule and/or thecharacter string extraction rule associated in advance with theattribute type custom token is set. Due to this, it is possible for auser to easily set a desired custom token to which the character stringverification rule and/or the character string extraction rule isattached. On the other hand, in a case where the radio button 2602 c isselected, the normalization rule is not set to the dropped attributetype custom token. In a case where the radio button 2602 b is selected,the setting to automatically delete characters, such as “Inc.” includedin the trade name, is performed for the dropped attribute type customtoken.

It may also be possible to change the display aspect of the attributetype custom token depending on the scan profile selected by a user andthe scan-target document type. For example, in a case where a scanprofile for a business card scan is created, as the attribute typecustom token that can be used for the folder allocation rule and thefile naming rule, only “Company name”, “Division”, “Name”, “Telephonenumber”, and “Mail address” are displayed, and so on. Further, it mayalso be possible to provide a text field so that a user can freelycustomize a regular expression or the like in a case where a desiredrule does not exist among alternatives within the context menu.

Furthermore, it may also be possible to enable a user to set thenormalization rule to the custom token at timing of selecting a textblock in the preview pane 1401 on the property setting screen 1400. FIG.27 shows the property setting screen 1400 in a case where the attributetype custom token that takes “Company name” as the attribute namethereof is set to the folder allocation rule and the file naming rule.Here, the state is such that an attribute value input field 2701 isselected and highlighted. In a case where a user places a mouse over atext block 2702 in this state, a pop-up menu 2073 is displayed under thetext block 2702. At this time, the contents displayed in the pop-up menu2703 are the character string verification rule and/or the characterstring extraction rule associated in advance with the attribute typecustom token of “Company name”. In this example, it is possible for auser to set the normalization rule to delete the characters of “Inc.”included in the trade name by selecting “Delete trade name” within thedisplayed pop-up menu. It may also be possible to enable a user toperform the setting of the normalization rule at the time of inputtingan attribute value.

According to this modification example, time and effort at the time ofsetting the normalization rule to a custom token are saved, andtherefore, it is made possible for a user to more easily make use of thecharacter string verification rule and the character string extractionrule.

As above, according to the present embodiment, it is possible for a userto easily create and edit the folder allocation rule and the file namingrule necessary at the time of filing a document scanned image or thelike and storing the file.

OTHER EMBODIMENTS

Embodiment(s) of the present disclosure can also be realized by acomputer of a system or apparatus that reads out and executes computerexecutable instructions (e.g., one or more programs) recorded on astorage medium (which may also be referred to more fully as a‘non-transitory computer-readable storage medium’) to perform thefunctions of one or more of the above-described embodiment(s) and/orthat includes one or more circuits (e.g., application specificintegrated circuit (ASIC)) for performing the functions of one or moreof the above-described embodiment(s), and by a method performed by thecomputer of the system or apparatus by, for example, reading out andexecuting the computer executable instructions from the storage mediumto perform the functions of one or more of the above-describedembodiment(s) and/or controlling the one or more circuits to perform thefunctions of one or more of the above-described embodiment(s). Thecomputer may comprise one or more processors (e.g., central processingunit (CPU), micro processing unit (MPU)) and may include a network ofseparate computers or separate processors to read out and execute thecomputer executable instructions. The computer executable instructionsmay be provided to the computer, for example, from a network or thestorage medium. The storage medium may include, for example, one or moreof a hard disk, a random-access memory (RAM), a read only memory (ROM),a storage of distributed computing systems, an optical disk (such as acompact disc (CD), digital versatile disc (DVD), or Blu-ray Disc (BD)™),a flash memory device, a memory card, and the like.

According to the technique of the present disclosure, it is madepossible to more easily set the rule relating to folder allocation andfile naming at the time of filing data, such as a document scanned imageand a received facsimile, and storing the file.

While the present disclosure has been described with reference toexemplary embodiments, it is to be understood that the disclosure is notlimited to the disclosed exemplary embodiments. The scope of thefollowing claims is to be accorded the broadest interpretation so as toencompass all such modifications and equivalent structures andfunctions.

This application claims the benefit of Japanese Patent Applications No.2020-061446, filed Mar. 30, 2020 and No. 2020-172746, filed Oct. 13,2020 which are hereby incorporated by reference wherein in theirentirety.

1.-12. (canceled)
 13. An information processing apparatus comprising: atleast one memory that stores a program; and at least one processor thatexecutes the program to: display, on a display, a user interface screenfor performing setting for generating a name related to a document,wherein items selected by a user from a plurality of items are arrangedon the user interface screen, wherein the plurality of items includes anitem for using, to generate the name, a character string that isobtained by applying a rule to an Optical Character Recognition (OCR)result to be obtained by performing OCR processing on an area designatedon the document, and wherein the user interface screen enables a user toperform a drag and drop operation on at least one of the arranged itemsto change the arrangement of the selected items; and perform the settingaccording to the changed arrangement of the selected items.
 14. Theinformation processing apparatus according to claim 13, wherein the nameis a file name of a file corresponding to the document.
 15. Theinformation processing apparatus according to claim 13, wherein the nameis a folder name of a folder to which a file corresponding to thedocument is to be stored.
 16. The information processing apparatusaccording to claim 13, wherein the name is a folder path including afolder name of a folder to which a file corresponding to the document isto be stored.
 17. The information processing apparatus according toclaim 13, wherein the at least one processor executes the program tofurther: perform the OCR processing on the area designated on thedocument to obtain the OCR result; and using the setting and theobtained OCR result, generate the name related to the document.
 18. Theinformation processing apparatus according to claim 13, wherein theplurality of items includes another item for using a variable, togenerate the name, not related to the OCR result.
 19. The informationprocessing apparatus according to claim 18, wherein the variablecorresponds to an environment variable of the user.
 20. The informationprocessing apparatus according to claim 18, wherein the variablecorresponds to a name of login user.
 21. The information processingapparatus according to claim 18, wherein the variable corresponds to adate and a time.
 22. The information processing apparatus according toclaim 21, wherein the setting for generating the item can be performedto insert a delimiter between the date and the time.
 23. The informationprocessing apparatus according to claim 22, wherein the data and thetime are related to when the document is received.
 24. The informationprocessing apparatus according to claim 18, wherein a delimiter is ableto be arranged between the arranged items.
 25. The informationprocessing apparatus according to claim 18, wherein the plurality ofitems further includes a different item corresponding a delimiter, andwherein the different item is able to be arranged between the arrangeditems.
 26. The information processing apparatus according to claim 13,wherein the rule is a rule for extracting the character string from theOCR result.
 27. The information processing apparatus according to claim13, wherein the rule is a rule for obtaining the character string bydeleting a part of the OCR result.
 28. A method executed by aninformation processing apparatus comprising at least one memory thatstores a program, and at least one processor that executes the programto execute the method, the method comprising: displaying, on a display,a user interface screen for performing setting for generating a namerelated to a document, wherein items selected by a user from a pluralityof items are arranged on the user interface screen, wherein theplurality of items includes an item for using, to generate the name, acharacter string that is obtained by applying a rule to an OpticalCharacter Recognition (OCR) result to be obtained by performing OCRprocessing on an area designated on the document, and wherein the userinterface screen enables a user to perform a drag and drop operation onat least one of the arranged items to change the arrangement of theselected items; and performing the setting according to the changedarrangement of the selected items.
 29. The method according to claim 28,wherein the name is a file name of a file corresponding to the document.30. The method according to claim 28, wherein the name is a folder nameof a folder to which a file corresponding to the document is to bestored.
 31. The method according to claim 28, wherein the name is afolder path including a folder name of a folder to which a filecorresponding to the document is to be stored.
 32. The method accordingto claim 28, wherein the at least one processor executes the program tofurther: perform the OCR processing on the area designated on thedocument to obtain the OCR result; and using the setting and theobtained OCR result, generate the name related to the document.
 33. Themethod according to claim 28, wherein the plurality of items includesanother item for using a variable, to generate the name, not related tothe OCR result.
 34. The method according to claim 33, wherein thevariable corresponds to an environment variable of the user.
 35. Themethod according to claim 33, wherein the variable corresponds to a nameof login user.
 36. The method according to claim 33, wherein thevariable corresponds to a date and a time.
 37. The method according toclaim 36, wherein the setting for generating the item can be performedto insert a delimiter between the date and the time.
 38. The methodaccording to claim 37, wherein the data and the time are related to whenthe document is received.
 39. The method according to claim 33, whereina delimiter is able to be arranged between the arranged items.
 40. Themethod according to claim 33, wherein the plurality of items furtherincludes a different item corresponding a delimiter, and wherein thedifferent item is able to be arranged between the arranged items. 41.The method according to claim 28, wherein the rule is a rule forextracting the character string from the OCR result.
 42. The methodaccording to claim 28, wherein the rule is a rule for obtaining thecharacter string by deleting a part of the OCR result.
 43. Anon-transitory computer-readable storage medium storingcomputer-executable code of a program that, when executed by a processorof an information processing apparatus, causes the informationprocessing apparatus to execute: displaying, on a display, a userinterface screen for performing setting for generating a name related toa document, wherein items selected by a user from a plurality of itemsare arranged on the user interface screen, wherein the plurality ofitems includes an item for using, to generate the name, a characterstring that is obtained by applying a rule to an Optical CharacterRecognition (OCR) result to be obtained by performing OCR processing onan area designated on the document, and wherein the user interfacescreen enables a user to perform a drag and drop operation on at leastone of the arranged items to change the arrangement of the selecteditems; and performing the setting according to the changed arrangementof the selected items.
 44. The non-transitory computer-readable storagemedium according to claim 43, wherein the name is a file name of a filecorresponding to the document.
 45. The non-transitory computer-readablestorage medium according to claim 43, wherein the name is a folder nameof a folder to which a file corresponding to the document is to bestored.
 46. The non-transitory computer-readable storage mediumaccording to claim 43, wherein the name is a folder path including afolder name of a folder to which a file corresponding to the document isto be stored.
 47. The non-transitory computer-readable storage mediumaccording to claim 43, wherein the at least one processor executes theprogram to further: perform the OCR processing on the area designated onthe document to obtain the OCR result; and using the setting and theobtained OCR result, generate the name related to the document.
 48. Thenon-transitory computer-readable storage medium according to claim 43,wherein the plurality of items includes another item for using avariable, to generate the name, not related to the OCR result.
 49. Thenon-transitory computer-readable storage medium according to claim 48,wherein the variable corresponds to an environment variable of the user.50. The non-transitory computer-readable storage medium according toclaim 48, wherein the variable corresponds to a name of login user. 51.The non-transitory computer-readable storage medium according to claim48, wherein the variable corresponds to a date and a time.
 52. Thenon-transitory computer-readable storage medium according to claim 51,wherein the setting for generating the item can be performed to insert adelimiter between the date and the time.
 53. The non-transitorycomputer-readable storage medium according to claim 52, wherein the dataand the time are related to when the document is received.
 54. Thenon-transitory computer-readable storage medium according to claim 48,wherein a delimiter is able to be arranged between the arranged items.55. The non-transitory computer-readable storage medium according toclaim 48, wherein the plurality of items further includes a differentitem corresponding a delimiter, and wherein the different item is ableto be arranged between the arranged items.
 56. The non-transitorycomputer-readable storage medium according to claim 43, wherein the ruleis a rule for extracting the character string from the OCR result. 57.The non-transitory computer-readable storage medium according to claim43, wherein the rule is a rule for obtaining the character string bydeleting a part of the OCR result.